Below is a basic overview on creating Vertical/ Horizontal Sametime Gateway cluster

Config Information on creating Vertical/ Horizontal Sametime Gateway cluster

Below is a basic overview on creating Vertical/ Horizontal Sametime Gateway cluster
The STGW Cluster configuration in our example has a Deployment Manager Server , SIP Proxy Server , and 2 Sametime Gateway servers
A Horizontal configuration is when you have 2 or more Gateway server systems..
A Vertical configuration is when you have 3 or more Gateway r instances running on the same server system.

1) Setting up the Horizontal STGW Cluster :
Set up your Deployment Manager, initial Gateway Sever , then add any additional Gateway Server nodes .
Follow directions to Install 1 STGW instance on each of your (Horizontal) Gateway server nodes . http://publib.boulder.ibm.com/infocenter/sametime/v8r0/topic/com.ibm.help.sametime.802.doc/Gateway/i_t_sametime_gateway_install.html
Follow the steps to federate primary node. Assure you add the first node WITH "-installapps" flag in the addnode command.
Follow the steps to add additional secondary STGW node(s) on the other server(s). Assure that you add a these secondary nodes WITHOUT specifying the "-installapps" flag in the Addnode command.
Follow the steps to Implement the ConfigWizard to create a Cluster .
Config Wizard will ask for a unique node name for the additional nodes Here is example of a 2 Node Horizontal cluster. You should have something like this when done.

Make sure that the Horizontal Cluster starts and the Applications start . For example.:


You have successfully created a Horizontal STGW Cluster

2) Install Updates:
If you plan on adding many secondary Gateway instances nodes , now is a good time to apply upgrade patches because it will save you time from upgrading the additional gateway instances later.

3) Setting up the Horizontal Gateway Cluster
Now that you have created the STGW nodes in your Horizontal Cluster, you can easily add additional cluster member instances on those same nodes by referencing the following steps
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/urun_rwlm_cluster_create3_v61.html

For Example :


Add instances Horizontally on server nodes . Assure that each STGW instance must have at least 2gb memory.

Manually configure your Host Alias ports for each Gateway Instance. Assure that ports are unique on each node.
Select System Administration -> Virtual Hosts > default_host > Host Aliases
Here is a example of the virtual port configurations:






You have successfully completed your Vertical Gateway Cluster installation

4 Complete steps to configuration Sip Proxy.
Follow the procedures to install the SIP Proxy. : http://publib.boulder.ibm.com/infocenter/sametime/v8r0/topic/com.ibm.help.sametime.802.doc/Gateway/i_rtc_t_install_sip_proxy_server.html

Open ISC : Proxy Servers > SIPProxyServer > SIPProxyServer and verify the cluster is defined in the "Default cluster " drop down
You will need to change default of "none" to "cluster " for SIP Proxy.
If you do not you will see this error message in the proxy log :
[6/24/09 7:08:24:126 EDT] 00000031 LookupLogger W CWSPX0010W: Unable to find least loaded server for request in cluster "" repeated 1 times with last failure 6/24/09 7:08:22:923 EDT

and those one in the server log

[6/24/09 17:41:19:711 EDT] 0000004a SIPCommonUtil E SIPCommonUtils sendMessage Can not send message got IOException: Cluster is not fully initiated, cannot send message.
[6/24/09 17:41:19:758 EDT] 0000004a SIPKeepAliveT W Failed to send out a keep-alive request to external community "acme" at port 5060. If the system is configured with a SIP Proxy, make sure the SIP Proxy is running.

Example to make sure the Sip Proxy is properly configured to supported the cluster :


5) Apply tuning settings
http://publib.boulder.ibm.com/infocenter/sametime/v8r0/topic/com.ibm.help.sametime.802.doc/Gateway/i_rtc_t_tuning.html